SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
 
Tags
    Impact
      Clean code attribute
        1. Using unsafe code blocks is security-sensitive

           Security Hotspot
        2. Not specifying a timeout for regular expressions is security-sensitive

           Security Hotspot
        3. Hard-coded secrets are security-sensitive

           Security Hotspot
        4. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        5. Deserializing objects without performing data validation is security-sensitive

           Security Hotspot
        6. Disabling ASP.NET "Request Validation" feature is security-sensitive

           Security Hotspot
        7. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        8. Using publicly writable directories is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        11. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        12. Configuring loggers is security-sensitive

           Security Hotspot
        13. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        14. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        15. Disabling CSRF protections is security-sensitive

           Security Hotspot
        16. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        17. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        18. Setting loose file permissions is security-sensitive

           Security Hotspot
        19. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        20. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        21. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        22. Formatting SQL queries is security-sensitive

           Security Hotspot
        23. Hard-coded credentials are security-sensitive

           Security Hotspot
        24. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Setting loose file permissions is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe

        In Unix, "others" class refers to all users except the owner of the file and the members of the group assigned to this file.

        In Windows, "Everyone" group is similar and includes all members of the Authenticated Users group as well as the built-in Guest account, and several other built-in security accounts.

        Granting permissions to these groups can lead to unintended access to files.

        Ask Yourself Whether

        • The application is designed to be run on a multi-user environment.
        • Corresponding files and directories may contain confidential information.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        The most restrictive possible permissions should be assigned to files and directories.

        Sensitive Code Example

        .Net Framework:

        var unsafeAccessRule = new FileSystemAccessRule("Everyone", FileSystemRights.FullControl, AccessControlType.Allow);
        
        var fileSecurity = File.GetAccessControl("path");
        fileSecurity.AddAccessRule(unsafeAccessRule); // Sensitive
        fileSecurity.SetAccessRule(unsafeAccessRule); // Sensitive
        File.SetAccessControl("fileName", fileSecurity);
        

        .Net / .Net Core

        var fileInfo = new FileInfo("path");
        var fileSecurity = fileInfo.GetAccessControl();
        
        fileSecurity.AddAccessRule(new FileSystemAccessRule("Everyone", FileSystemRights.Write, AccessControlType.Allow)); // Sensitive
        fileInfo.SetAccessControl(fileSecurity);
        

        .Net / .Net Core using Mono.Posix.NETStandard

        var fileSystemEntry = UnixFileSystemInfo.GetFileSystemEntry("path");
        fileSystemEntry.FileAccessPermissions = FileAccessPermissions.OtherReadWriteExecute; // Sensitive
        

        Compliant Solution

        .Net Framework

        var safeAccessRule = new FileSystemAccessRule("Everyone", FileSystemRights.FullControl, AccessControlType.Deny);
        
        var fileSecurity = File.GetAccessControl("path");
        fileSecurity.AddAccessRule(safeAccessRule);
        File.SetAccessControl("path", fileSecurity);
        

        .Net / .Net Core

        var safeAccessRule = new FileSystemAccessRule("Everyone", FileSystemRights.FullControl, AccessControlType.Deny);
        
        var fileInfo = new FileInfo("path");
        var fileSecurity = fileInfo.GetAccessControl();
        fileSecurity.SetAccessRule(safeAccessRule);
        fileInfo.SetAccessControl(fileSecurity);
        

        .Net / .Net Core using Mono.Posix.NETStandard

        var fs = UnixFileSystemInfo.GetFileSystemEntry("path");
        fs.FileAccessPermissions = FileAccessPermissions.UserExecute;
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • OWASP - Top 10 2021 Category A4 - Insecure Design
        • OWASP - Top 10 2017 Category A5 - Broken Access Control
        • OWASP File Permission
        • CWE - CWE-732 - Incorrect Permission Assignment for Critical Resource
        • CWE - CWE-266 - Incorrect Privilege Assignment
        • STIG Viewer - Application Security and Development: V-222430 - The application must execute without excessive account permissions.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use